Skip to content

Conversation

meisterT
Copy link
Member

While you can select the new types, they won't function yet.

Part of #2525

Problem types are defined here: https://icpc.io/problem-package-format/spec/2023-07-draft.html#type

@meisterT meisterT force-pushed the newtypes branch 2 times, most recently from 8289465 to 9251876 Compare March 29, 2025 16:24
@meisterT meisterT force-pushed the newtypes branch 4 times, most recently from 570510e to 4d6d542 Compare March 30, 2025 11:39
@meisterT meisterT marked this pull request as ready for review March 30, 2025 11:39
While you can select the new types, they won't function yet.

Part of DOMjudge#2525

Problem types are defined here: https://icpc.io/problem-package-format/spec/2023-07-draft.html#type
@meisterT meisterT added this pull request to the merge queue Apr 6, 2025
Merged via the queue into DOMjudge:main with commit a59ab57 Apr 6, 2025
36 checks passed
@meisterT meisterT deleted the newtypes branch April 6, 2025 18:51
Comment on lines +341 to +343
if (!($this->types & self::TYPE_PASS_FAIL) xor ($this->types & self::TYPE_SCORING)) {
throw new Exception("Invalid problem type: must be exactly one of 'pass-fail' or 'scoring'.");
}
Copy link
Contributor

@mpsijm mpsijm Apr 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that pass-fail is implied when it is not provided. For example, type: interactive implies type: [pass-fail, interactive]. I noticed this when doing a test upload today 😂

See also: Kattis/problem-package-format#440

EDIT: Looks like this was fixed in 2b7adab (#2999), thanks! ❤️

It's now also in the spec, see Kattis/problem-package-format#471 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants